I just noted a small "bug" probably present in all versions of SD. When planning a border crossing flight and adding a published border crossing reporting point, SD will still add its own border crossing point in the flightplan in lat/lon notation. To wit, a flight from Graz (LOWG) to Maribor (LJMB) with a border crossing point of OLMOT will still insert another border crossing point.

I suggest to omit the calculated crossing point in case there already is a waypoint in the flightplan which is within 5 miles (measured along the planned route) of the physical border crossing.

Also, what were thise superfluous DCT's in the route portion? In Austria this drives the controller crazy. Have got an admonishing call twice because of them.

-- Chris.